This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: Preventing access to a local replica ~Umberto Nongeroson 6.Jan.04 08:08 PM a Web browser Notes Client All ReleasesAll Platforms
There's no direct way to do what you're asking for here. If a local system is not in touch with the server, it has no way to tell whether the userid is still authorized on the server. I assume you do want your sales force to be able to use disconnected local replicas on the road.
You could, however, do things to make a local replica extremely difficult to use after some period of time has elapsed without replication. Write an agent that daily updates some special document. Choose a cutoff, say 4 weeks. Add code to the database Postopen event to see whether this is a local replica and to check the last modified time of this special document. If it hasn't been updated in the last 4 weeks, hard delete all the documents in the database (or use an API function to set the replication cutoff to zero days, making all the documents vanish without leaving pesky deletion stubs. Or delete the database itself).
Or you could employ a password locked system. Have a secret algorithm in the database to generate an access password which changes every week. Have an agent email next week's password to each authorized user weekly. On database open, challenge for the password. If they don't get it, kick 'em out.
Return to top
. . RE: Preventing access to a local re... (~Bill Frokimari... 6.Jan.04) 
Print this page
